Touch screen interface and infrared communication system integrated into a battery

ABSTRACT

Apparatuses and methods relating to interfacing and controlling external batteries are described. In one embodiment, an external battery is integrated with a touch screen display. In one embodiment, the external battery provides an infrared communication link with a detachable device or system controller. In one embodiment, the external battery touch screen interface provides data received from a detachable device or system controller.

CROSS-REFERENCE

This application is a continuation of co-pending U.S. application Ser.No. 14/944,159 filed on Nov. 17, 2015, which is a continuation of U.S.application Ser. No. 14/455,843 filed on Aug. 8, 2014 (now issued asU.S. Pat. No. 9,195,289), which is a continuation of U.S. applicationSer. No. 13/894,284 filed on May 14, 2013 (now issued as U.S. Pat. No.8,827,890), which claims the benefit of U.S. Provisional ApplicationSer. No. 61/648,428, filed on May 17, 2012, and this provisionalapplication is hereby incorporated herein by reference.

FIELD

Embodiments described herein generally relate to an external battery.

COPYRIGHT NOTICE/PERMISSION

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever. The following notice applies: Copyright 2012,Thoratec Inc., All Rights Reserved.

BACKGROUND

Users of portable devices generally prefer small and light devices tolarger, heavier alternatives. Portable medical devices such ascontrollers of mechanical circulatory systems (MCS) are carried on aperson at all times and thus benefit greatly from a small portabledesign. One type of MCS is a ventricular assist device (VAD). Achallenge for manufacturers is to reduce the size and weight of deviceswhile still providing the reliability and ease of usability that usersexpect.

VADs are implanted in a patient and controlled by a system controllerthrough a percutaneous connection. The VAD comprises a heart pump toprovide assisted blood flow for a patient. A percutaneous (drive line)connection couples the system controller, comprising a motor controllerand one or more batteries, to the implanted heart pump. Ventricularassist systems with their coupled system controller must provide foruninterrupted blood flow assistance for the patient (user) and thereforebenefit from a design that is portable as well as robust.

VADs have typically been implanted for use in late stage heart failure(Class IV) patients. Some VAD systems allow patients to carry a portablesystem controller and batteries to allow for untethered operation oftheir heart pump. Typically, these patients can attain a high degree ofmobility and freedom, as demonstrated by quality of life measures,however the peripheral devices (including the system controller andbatteries) the patients must carry and manage remain cumbersome.Adoption of VAD systems is expected to expand to include less-sick (i.e.Class III) heart failure patients. Patient quality of life will be asignificant factor in determining VAD acceptance with Class IIIpatients. Therefore, more robust and intelligent device connections areneeded to provide decreased risk of infection, decreased risk of powerfaults, and greater ease of use for patients.

Current VAD systems are easily identifiable as a medical device and canrequire two or more large batteries worn on the patient. Often eachbattery is coupled to the system controller by a long cable connectionto allow for even weight distribution of each battery located externallyfrom the system controller. More cables, connections, and weight createa greater likelihood of trauma to the exit site during routine movementsof the patient. It is preferable for patients to have a device smallenough to conceal beneath clothing. Also, from a quality of lifeperspective, patient worn peripherals should be as unobtrusive to thepatient as possible. VAD cables can tangle and cause undue stress to anexit site where the percutaneous connection leaves the body. Stress atthe exit site leads to skin breakdown or trauma and put the patient atrisk of infection. Furthermore, the current cables and electricalconnections result in components that are susceptible to water, dust orother elements. Devices having multiple exposed electrical connectionsalso contain a higher risk of shorting out the medical device throughunintended connections. Patients using current systems must take specialcare when maintaining and using their devices.

Current medical devices also do not allow for multiple input and outputoptions for their medical devices. Patients must choose systems withadvanced touch screen interfaces that are relatively large, or choosesmaller but potentially less flexible displays with separate buttons orswitches. Therefore, greater flexibility for VAD systems is needed inorder to allow their device to be as portable as possible in certainsituations, without sacrificing usability.

SUMMARY OF THE DESCRIPTION

In one embodiment, a data connection is established between an externalbattery and a detachable device (e.g., a patient device or systemcontroller). In one embodiment, the external battery provides power tothe detachable device and a data communication link is establishedbetween the external battery and detachable device. In one embodiment, arepresentation of data sent between the external battery and thedetachable device is displayed on a touch screen integrated into theexternal battery. In one embodiment, the external battery can providepower to the detachable device, which can be a system controller for anMCS such as a left ventricular assist device, and can also provide powerto the MCS; in one embodiment, the power is provided only after awireless (e.g., infrared) data connection is established between thedetachable device and the external battery.

In one embodiment, a removable external battery with an integrated touchscreen display is coupled to a system controller. In one embodiment, thedisplay on the external battery provides additional or duplicate statusas the system controller.

In one embodiment, a system controller and an external battery arecommunicatively coupled together with an infrared data link.

In one embodiment, the system controller can send and receive data fromthe external battery through the infrared data link. In one embodiment,the data is one or more of alarm status, event history, pump parameters,log data, and power source status. In one embodiment, pump parametersare one or more of estimated fluid (e.g., blood) flow in the pump, fluid(e.g., blood) pressure, voltage values, phase current, and quiescent(IQ) current.

In one embodiment, the system controller controls a heart pump, and dataassociated with the heart pump is sent and received by the externalbattery. In one embodiment, the external battery displays data on anintegrated touch screen that is integrated with a display on theexternal battery.

In one embodiment, the external battery provides power to the systemcontroller after establishing the infrared data link. In one embodiment,power provided by the external battery is a secondary power source forthe system controller.

In one embodiment, magnets, electromagnets or mechanical connectionsbetween the components in a system allow for a controlled breakawaysequence. In one embodiment, a power adapter, system controller, andexternal battery implement a controlled breakaway connection system suchthat the power adapter is the first component to breakaway when thesystem is under external mechanical stress.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and not by wayof limitation, in the figures of the accompanying drawings in which likereferences indicate similar elements.

FIG. 1 illustrates, in block diagram form, an exemplary ventricularassist system connecting a pump, system controller, external battery,and a power adapter (such as an adapter that can charge the externalbattery and a battery within the system controller);

FIG. 2 illustrates, in block diagram form, an exemplary systemcontroller;

FIG. 3 illustrates, in block diagram form, an exemplary external batteryfor use with a system controller;

FIG. 4 is a flow chart illustrating a method for interacting with thetouch screen integrated into an external battery pack;

FIG. 5 is a projected view illustrating one embodiment of a systemcontroller;

FIG. 6 is a projected view illustrating one embodiment of a systemcontroller further coupled to an external battery;

FIG. 7 is a flow chart illustrating a method for providing power to aset of output terminals; and

FIG. 8 is a flow chart illustrating a method for providing a dataconnection and power between an external battery and a detachabledevice.

FIG. 9 is a projected view illustrating of one embodiment of a systemcontroller coupled to an external battery and percutaneous lead;

FIG. 10 is a projected view illustrating of one embodiment of a systemcontroller coupled to an external battery and percutaneous lead;

FIG. 11 is a perspective view illustrating of one embodiment of a systemcontroller coupled to an external battery and percutaneous lead;

FIG. 12 is a perspective view illustrating of one embodiment of a systemcontroller coupled to a power adapter and percutaneous lead;

FIG. 13 is a projected view illustrating of one embodiment of a systemcontroller coupled to a power adapter and percutaneous lead;

FIG. 14 is a projected view illustrating of one embodiment of a systemcontroller coupled to a power adapter and percutaneous lead;

FIG. 15 is a projected view illustrating one embodiment of a systemcontroller coupled to a power adapter and percutaneous lead;

FIG. 16 is a projected view illustrating one embodiment of a systemcontroller coupled to a power adapter and percutaneous lead;

FIG. 17 is a perspective view illustrating one embodiment of a systemcontroller coupled to a percutaneous lead and decoupled from a poweradapter;

FIG. 18 is a projected view illustrating one embodiment of a systemcontroller coupled to a percutaneous lead and decoupled from a poweradapter;

FIG. 19 is a perspective view illustrating one embodiment of a poweradapter;

FIG. 20 is a projected view illustrating one embodiment of a poweradapter;

FIG. 21 is a projected view illustrating one embodiment of a poweradapter having magnetic connections, and power connections;

FIG. 22 is a perspective view illustrating one embodiment of a poweradapter having magnetic connections, and power connections;

FIG. 23 is a partial perspective view illustrating one embodiment of apower adapter having magnetic connections, and power connections;

FIG. 24 is a projected illustrating one embodiment of a power adapterhaving magnetic connections, and power connections;

FIG. 25 is a partial perspective view illustrating one embodiment of apower adapter having magnetic connections, and power connections;

FIG. 26 is a projected view illustrating one embodiment of a poweradapter having magnetic connections, and power connections;

FIG. 27 is an exploded view illustrating one embodiment of a poweradapter having magnetic connections, and power connections;

FIG. 28 is an exploded view illustrating one embodiment of a poweradapter power cable, power connections and magnets;

FIG. 29 is a projected view illustrating one embodiment of a poweradapter power cable, power connection and magnets;

FIG. 30 is a projected view illustrating one embodiment of a poweradapter power cable connection;

FIG. 31 is a projected view illustrating one embodiment of a poweradapter power cable connection;

FIG. 32 is a projected view illustrating one embodiment of a poweradapter power cable connection;

FIG. 33 is a projected view illustrating one embodiment of a poweradapter power cable connection;

FIG. 34 is a projected view illustrating one embodiment of a poweradapter having magnetic connections, and power connections;

FIG. 35 is a projected view illustrating one embodiment of a poweradapter having magnetic connections, and power connections;

FIG. 36 is a projected view illustrating one embodiment of a poweradapter having magnetic connections, and power connections;

FIG. 37 is an perspective view illustrating one embodiment of a poweradapter power cable housing; and

FIG. 38 is a partial perspective view illustrating one embodiment of apower adapter power cable housing.

DETAILED DESCRIPTION

Various embodiments and aspects of the invention(s) will be describedwith reference to details discussed below, and the accompanying drawingswill illustrate the various embodiments. The following description anddrawings are illustrative of the invention and are not to be construedas limiting the invention. The term “coupled” as used herein, may meandirectly coupled or indirectly coupled through one or more interveningcomponents. Numerous specific details are described to provide athorough understanding of various embodiments of the present invention.However, in certain instances, well-known or conventional details arenot described in order to provide a concise discussion of embodiments ofthe present inventions.

Overview

Throughout the description, the methods, apparatuses, and systems of thepresent invention are discussed in the context of a ventricular assistsystem (VAS, such as a left ventricular assist device (LVAD)). It willbe appreciated, however, that these methods, apparatuses, and systemsare equally applicable to other types of mechanical circulatory systems(MCS). FIG. 1 illustrates one embodiment of a ventricular assist system(VAS) including a pump 110, system controller 125, external battery 145,and power adapter 155. In one embodiment, pump 110 is a heart blood pump(e.g., a rotary or similar pump for providing flow of blood) implantedin the user. In one embodiment, pump 110 assists a patient's heart tomaintain a steady flow of blood throughout their body. Pump 110continuously offloads blood from the left ventricle of the heart andpropels the blood into the aorta at a steady rate controlled by systemcontroller 125.

In one embodiment, system controller 125 provides interface and controlfunctions for pump 110. One of skill in the art, however, will recognizesystem controller 125 can control any device operative by an externalcontroller. In one embodiment, system controller 125 provides one ormore of the functions of motor commutation, power management, conditionsensing, data logging and communication, and/or user input/output. In anexemplary embodiment, system controller 125 is coupled to drive line 115(percutaneous lead) coupling pump 110 to system controller 125.

In one embodiment, system controller 125 can connect to external battery145 and power adapter 155 by connections 135 and 130, respectively. Inone embodiment, connections 135 and 130 are one or more ofelectromagnetic, magnetic, or mechanical ports that allow for acontrolled breakaway sequence when stress is applied to any of thesystem components. Further details of connections 135 and 130 andvarious embodiments of a controlled breakaway sequence are describedbelow.

In one embodiment, the system controller's drive line 115 connectiondesign allows for 360-degree axial rotation intended to minimize traumato the exit site, and reduce torsional stress on the drive line. Stresson the exit site can cause skin trauma leading to greater risk ofinfections. Reduced stress on drive line 115 improves cable managementfor a patient and allows for greater freedom of movement.

System Controller

FIG. 2 illustrates an exemplary system controller 125 that can detect,store, and utilize system-operating parameters associated operation ofpump 110. In one embodiment, system controller 125 maintains constantcommunication and control over an external motor in external pump 110.System controller 125 can provide power to and regulate the speed ofpump 110 through electrical signals transmitted by a percutaneous lead(drive line 115) extending through the skin of patient 105 with pump 110implant. System controller 125 can also receive data back from pump 110(e.g., electromotive force data or signals used to determine the speedof the pump). In one embodiment, system controller 125 provides one ormore of interpreting and responding to system performance, performingdiagnostic monitoring, indicating hazard and advisory alarms, providinga complete backup system, and event recording capability.

In one embodiment, one or more processors 210 in system controller 125execute instructions in memory 205 to maintain the power and functionsof pump 110. Processor 210 can be a programmable microcontroller,microprocessor or other similar device capable of executinginstructions. Processor as used herein can refer to a device having twoor more processing units or elements, e.g., a CPU with multipleprocessing cores. Memory 205 can include dynamic random access memoryand a memory controller that controls the operation of the memory.Memory 205 can also include a non-volatile read only and/or re-writablememory for storing data and software programs. Memory 205 can contain aprogram or instructions that controls the operation of processor 210 andalso can contain data used during the processing of controls for pump110. In one embodiment further described below, memory 210 includes acomputer program or instructions, which causes processor 210 tocommunicate to external battery 145.

In one embodiment, system controller 125 comprises one or moreintegrated batteries 230, power controller 225 and motor drivecontroller 220. Power controller 225 can regulate, control and/or managepower usage of system controller 125, motor drive controller 220 orother system controller 125 components. Power controller 225 can beconnected to motor drive controller 220 by power connection 255. In oneembodiment, external battery 145 and/or power adapter 155 is connectedto system controller 125 to provide power in addition to or instead ofinternal battery 230. Power controller 225 can receive and distributepower from one or more of internal battery 230 (over power line 260),external battery 145 (over power line 140), or power adapter 155 (overpower line 150). Power adapter 155 can be an AC/DC power adapter (e.g.,a standard home plug adapter or other AC source adapter) or a DC poweradapter (e.g., a car cigarette lighter adapter, or other DC sourceadapter). In one embodiment, motor 220 is coupled to drive line 115 toassist pump 110. In one embodiment, system controller 125 is a differenttype of detachable device, for example another type of medical device,consumer electronic device or other device that is detachable (e.g.,able to be decoupled) from an external connection and/or externalbattery.

Memory 205, one or more processors 210, power controller 225 andinput/output controller 215 can be separate components or can beintegrated in one or more integrated circuits. The various components insystem controller 125 can be coupled by one or more communication busesor signal lines 265.

In one embodiment, Input/Output controller 215 enables system controller125 to communicate with external battery 145. In other embodimentsfurther described below, memory 205 includes instructions for wirelesscommunication with other data processing systems or devices (separatefrom or in addition to external battery pack 145). In one embodiment,memory 205 also includes instructions to implement the various otherfeatures of the system controller 125 described below.

System controller 125 can also include network interface 250. Networkinterface 250 allows system controller 125 to communicate, in oneembodiment, to other processing systems through a wireless (e.g.,Bluetooth, Infrared Data Association (IrDA), WiFi, or other) protocol.In one embodiment, network interface 250 implements a wireless interfacesuch that no external physical connection is required for networking orexternal communication. Reducing or eliminating external wiredconnections is beneficial for maintaining a sealed waterproof or waterresistant environment to house system controller 125. Network interface250 is coupled to bus 265 so that system controller 125 can receivedata, such as communication from an external device (e.g., tablet,personal computer, or external battery) and send data to/from processor210 and memory 205.

In one embodiment, system controller 125 interfaces with an externalbattery comprising touch screen interface 330. In one embodiment, systemcontroller 125 uses touch screen 330 to display system controller 125notifications and status. Touch screen 330 can be a capacitive orresistive transparent input device that is overlaid on a display such asan LCD (Liquid Crystal Display) device such that the touch screenprovides both input and output capabilities. System controller 125 canalso have one or more integrated status displays separate from thedisplay utilized through external battery 145. For example, systemcontroller 125 can have various integrated displays (e.g., several LEDs)including one or more of a battery gauge, alarm notification, batterysymbols, pump status, or other representations of VAS status.

In one embodiment, system controller 125 includes one or moreinput/output (I/O) devices and/or sensor devices. In one embodiment, I/Odevices include one or more of display 240, an audio device (e.g.,speaker), a vibration motor, input device (e.g., buttons, knobs, levers,dials or similar controls), and one or more alarms 245. I/O controller215 interfaces with I/O devices integrated with or coupled with systemcontroller 125. I/O devices can be coupled to bus 265 and can send andreceive data from I/O controller 215. I/O controller 215 can alsointerface with external devices through input 235.

In one embodiment, display 240 is a segment display, LED display,full-area 2-dimensional display or other display capable of providing auser with visual indication of status or performance of systemcontroller 125.

In one embodiment, system controller 125 includes circuitry and sensorsfor supporting a positioning system, such as that provided by the globalpositioning system (GPS), a cellular communication system,accelerometer, compass, wireless network, or other method fordetermining the geographic positioning or relative movement. In oneembodiment, system controller 125 records positioning information ofsystem controller 125 (e.g., from an accelerometer or GPS). In oneembodiment, system controller 125 utilizes positioning information toestimate and record patient activity levels. In one embodiment, patientactivity information is stored in memory 205 and can be retrieved orsent to an external device. Recording patient activity levels for lateranalysis by a medical professional can improve quality of patient careby providing a record of patient activity. Otherwise, a medicalprofessional or technician must instead rely upon the patient's memoryto recall past events and estimated activity levels.

In one embodiment, system controller 125 generates diagnosticinformation. Diagnostic information is stored in memory 205 for realtime analysis or later retrieval and analysis by an external device(data processing system, tablet, computer, specialized device).

System controller 125 receives user or patient input and outputinformation through a user interface. In one embodiment, systemcontroller 125 has a segmented display and/or one or more LED or othertype of light to indicate status. In one embodiment, symbols or icons onsystem controller 125 are backlit when their status is active. Forexample, a power symbol icon may be used to indicate power status. A redheart symbol can be used to show overall status of the heart pump. Anaudio symbol button can be used to silence alarms. A series of lightscan be used to indicate battery level or charge status. A battery iconcan be used to show health of the battery.

In one embodiment, system controller 125 is mechanically coupled toexternal battery 145. In one embodiment, external battery 145 is able tosend and receive data to system controller 125 via one or more wirelesscommunications link (e.g., infrared). A wireless transfer protocol(e.g., infrared) obviates the need for a wired link between systemcontroller 125 and external battery 145 to facilitate a waterproofenclosure while retaining a robust mechanical design (i.e., noelectromechanical connector). In one embodiment, system controller 125uses infrared hardware 216 to communicate through infrared with externalbattery 145 which includes infrared hardware 316. In one embodiment,infrared hardware 216 and 316 are infrared transceivers that allow forinfrared data communication between two or more devices.

In one embodiment, system controller 125 includes network interface 250for one or more wireless protocols (e.g., Bluetooth, Infrared, WiFi, orother form of wireless communication link). Network interface 250 allowssystem controller 125 to communicate to other data processing systems ordevices through a wireless network connection. In one embodiment,wireless network interface 250 is used so that the need for externalphysical connections can be minimized or entirely removed. Reducing oreliminating external wired connections is beneficial for maintaining asealed waterproof or water resistant environment to house systemcontroller 125. In one embodiment, network interface 250 is coupled tobus 265. In one embodiment, bus 265 is coupled to processor 210 andmemory 205 of system controller 125. In one embodiment, networkinterface 250 sends and receives data to one or more of external battery145 and/or external device 270 (e.g., tablet, personal computer, PDA,smartphone, specialized medical device, or other data processingsystem).

In one embodiment, external device 270 connects to system controller 125to download and/or upload data stored in memory 205 of system controller125. In one embodiment, external device 270 sets, changes, and/orreceives pump 110 parameters. In one embodiment, pump 110 parametersinclude one or more of pump speed, estimated flow, DC bus voltage, phasecurrent, and quiescent current. For example, in a clinical setting atechnician can wirelessly connect from external device 270 to systemcontroller 125 to setup the VAS for the first time, and/or to makechanges to existing pump 110 settings. By using external device 270, atechnician can manage pump 110 settings of system controller 125 tostart, stop or otherwise modify the operation of pump 110. In otherembodiments, external device 270 can upload or update commands,firmware, software and/or programs on system controller 125.

In one embodiment, external device 270 sets, changes, and/or receivesother parameters (separate from pump control). In one embodiment, otherparameters include one or more of accelerometer data, alarm information,log data (including alarm and event history), power source status, powersource runtime information, and other data. In one embodiment, once aparameter is set or changed, the updated parameter(s) are stored inmemory 205 such that decoupling system controller 125 from the externaldevice 270 maintains parameter(s) in system controller 125.

Wireless transfer of data between system controller 125 and externaldevices facilitates efficient patient management. In one embodiment,external device 270 described above is a base station used by aclinician or medical professional to monitor the VAS and patient. Thebase station can receive and send the data and parameters to systemcontroller 125 as described above. In one embodiment, the base stationis configured to mirror the alarms and notifications of systemcontroller 125. In one embodiment, base station uploads commands tomodify settings of system controller 125 and receives real time feedbackas to the success of the commands.

In one embodiment, data and parameters on system controller 125 are sentto external battery 145. In one embodiment, external battery 145receives data from system controller 125 and outputs the data to adisplay on external battery 145. Further details regarding the datadisplayed on the external battery 145 are discussed below.

External Battery

FIG. 3 illustrates an exemplary external battery 145 with touch screen330 for use with system controller 125. In one embodiment, one or moreprocessors 310 in external battery 145 executes instructions in memory305 to establish and maintain communication with system controller 125,receive input from touch screen 330 and output data to display 325.Processor 310 can be a programmable microcontroller, microprocessor orother similar device capable of executing instructions. Processor asused herein can refer to a device having two or more processing units orelements, e.g., a CPU with multiple processing cores. In one embodiment,external battery 145 includes memory 305. Memory 305 can include dynamicrandom access memory (DRAM) and a memory controller that controls theoperation of the memory. Memory 305 can also include a non-volatile readonly and/or re-writable memory for storing data and software programs.Memory 305 can contain a program or instruction set that controls theoperation of processor 310. For example, memory 305 can be anon-transitory computer readable storage medium that stores one or morecomputer programs that when executed by processor 310 perform one ormore methods described herein such as the methods shown in FIG. 4 or 7or 8. Memory 305 can also contain data or instructions used duringcommunication with system controller 125 and data or instructions foroperating touch screen 330 and display 325. Touch screen 330 is capableof receiving direct user input through touch (e.g., touch of a humanuser's finger(s)) and/or, a stylus. Display 325 is capable of providingvisible output to the user. In one embodiment, touch screen 330 anddisplay 325 are integrated into one unit, an example of which is shownas touch screen 610 in FIG. 6. In one embodiment further describedbelow, memory 305 includes a computer program or instructions, whichcauses processor 310 to control alarm 335. In one embodiment, alarm 335includes one or more hazard alarms mirrored from system controller 125.

External battery 145 includes one or more integrated batteries 320. Inone embodiment, external battery 145 provides supplemental power tosystem controller 125. In the case of failure or removal of externalbattery 145, system controller 125 can automatically switch to internalbattery 230 and continue to provide power and control for pump 110. Inone embodiment, power adapter 155 can be coupled to external battery 145to charge one or more integrated batteries 320. Memory 305, one or moreprocessors 310, touch screen 330, display 325, and one or more alarms335 can be separate components or can be integrated in one or moreintegrated circuits. Alarm 335 can include one or more of a speaker foroutput of audio, motor for providing vibration, and visual on display325. One or more communication buses or signal lines 321 can couple thevarious components in external battery 145.

In one embodiment, Input/Output controller 315 enables external battery145 to communicate with system controller 125. In other embodimentsfurther described below, memory 305 includes instructions for wirelesscommunication with other data processing systems or devices (separatefrom the system controller 125). In one embodiment, memory 305 alsoincludes instructions to implement the various other features of theexternal battery pack 145 described below.

In one embodiment, external battery pack 145 contains integrated touchscreen 330 and display 325. Touch screen 330 on external battery 145enables a user to request and receive updates from system controller 125and external battery 145 without the need for accessing controls onsystem controller 125. In one embodiment, pump 110 parameters fromsystem controller 125 are received and displayed on touch screen 330. Inone embodiment, touch screen 330 can display a representation of one ormore of pump speed, estimated flow, power measurement, and a pulsatilityindex parameter.

In one embodiment, touch screen 330 configures or displays alarminformation on system controller 125. Further details on the alarm onsystem controller 125 as well as the ability to mirror alarms onexternal battery 145 are discussed below. System controller 125 can logtime-stamped data and events (e.g., power source changes, suctionevents, and other events) that can be output to touch screen 330. In oneembodiment, touch screen 330 can present a series of the most recentevents to assist in remote or local troubleshooting. For example, apatient on the phone with a technician can recall the last set of eventsthat occurred on system controller 125 in order to discuss VAS historywith a remote technician. In one embodiment, touch screen 330 has a userinterface that includes multiple screens and menu options for accessinginformation related to system controller 125 and/or one or more otherdevice(s) connected to external battery 145. For example, alarm history,trending data, power source runtime information and other details can beaccessible through touch screen 330 interface.

Touch screen 330 on external battery 145 allows for system controller125 to be designed with less weight, size, and electrical complexity. Asdiscussed above, system controller 125 provides critical monitoring andcontrol of heart pump 110. Locating potential points of failure to aless critical and easily replaceable external battery 145 extends thelongevity and reliability of system controller 125. For example,external battery 145 can be decoupled to allow for the smallest formfactor possible during stand-alone operation system controller 125. Inone embodiment, while external battery 145 is decoupled, systemcontroller 125 automatically switches to internal battery 230 and pump110 continues to operate.

In addition, relegating a heavily used component (touch screen 330interface) to a relatively inexpensive and easily replaceable externalbattery 145 provides less wear and tear on system controller 125.Furthermore, the fact that touch screen 330 is located externally fromsystem controller 125 minimizes the possibility that damaging touchscreen 330 will electrically affect the system controller'sfunctionality. An external touch screen 330 also minimizes interactionsbetween the software driving system controller 125 and the softwaredriving touch screen 330.

As discussed above, one embodiment of system controller 125 has auser-interface consisting of buttons (e.g., push-buttons) and a display(e.g., LED). Replacing buttons and a display with touch screen 330 largeenough for large icons and written textual descriptions and icons wouldbe prohibitively large for system controller 125. Integrating touchscreen 330 with large battery maintains the portability of systemcontroller 125 when external battery 145 is decoupled.

In one embodiment, integrating touch screen 330 and glass/plastic frontscreen cover into external battery 145 reduces the weight of systemcontroller 125 by more than half Separating touch screen 330 from systemcontroller 125 also provides benefits in terms of programmingextensibility, regulatory compliance, and failure mode analyses. Using aseparate processor 310 from processor 210 in system controller 125allows the icons, screen layouts, text language, and other options to bechanged without altering the instructions or programs of systemcontroller 125. Other display 325 related modifications include one ormore of adding additional language support, user interface modificationsto accommodate the latest clinical usages and needs, and allowing usersto view the heart pump's operational data/history. Touch screens aretypically subject to heavy use and can be subjected to excessivepressure by users. Touch screens may also be susceptible to scratchingand cracking of the glass or plastic housing. Separating touch screen330 from system controller 125 allows system controller 125 to continueoperating unaffected if touch screen 330 or display 335 are damaged. Inone embodiment when processor 310 in external battery 145 is damaged orsuffers from instruction errors/faults, system controller 125 andexternal battery 145 are unaffected. Because system controller 125 andexternal battery 145 are separated by an infrared communications link,there is no possibility of touch screen 330 or display 325 electricallyinterfering with the system controller's operation of pump 110. Adamaged external battery 145 is easily replaced with a new externalbattery 145 without interruption of pump 110. In one embodiment,external battery 145 or other similarly connected device cannot changecontrols related to pump 110 but can receive status updates or pump 110statistics.

FIG. 4 is a flow chart illustrating an exemplary method 400 forreceiving and displaying data on a touch screen integrated into abattery. For example, method 400 may be performed by external battery145.

At block 405, external battery 145 receives a request on integratedtouch screen 330. In one embodiment, the user or patient touches touchscreen 330 on external battery 145 to make a selection. In otherembodiments, the patient uses a stylus or other interface to make aselection on the screen. For example, the patient may request the statusof pump 110 (e.g., current blood flow estimation) by pressing on a pumpicon represented on touch screen 330.

At block 410, external battery 145 determines that data from adetachable device can fulfill the request initiated on touch screen 330.In one embodiment, the detachable device is system controller 125. Forexample, current blood flow estimation can be determined by datareceived or read from system controller 125.

At block 415, external battery 145 establishes a data connection betweenexternal battery 145 and a detachable device (e.g., system controller125). This data connection can be through infrared hardware on bothsystem controller 125 and external battery 145. In one embodiment,external battery 145 requests data from system controller 125 afterreceiving input on touch screen 330. In other embodiments, systemcontroller 125 detects the connection to external battery 145 andprovides a stream of relevant and associated data to external battery145 such that system controller 125 does not need to process requests.For example, upon detecting that external battery 145 is connected,system controller 125 provides real time updates to external battery 145and external battery 145 can store the updates in memory 305 forprocessing by processor 310.

At block 420, external battery 145 establishes a power connectionbetween external battery pack 145 and the detachable device. In oneembodiment, a power connection is created after determining that a dataconnection to the detachable device is established.

At block 425, external battery 145 transfers data between externalbattery 145 and the detachable device. In one embodiment, externalbattery 145 requests data from the detachable device. In otherembodiments, the detachable device provides a stream of real time dataand external battery 145 processes all data and displays only requestedor relevant data to the user.

At block 430, external battery 145 processes data received from thedetachable device. In one embodiment, external battery 145 formats theprocessed data for display on display 325. For example, after a requestfor blood pump flow information, the current blood pump flow isdisplayed on touch screen 330.

Redundant and Safe Power Management

In one embodiment, system controller 125 provides uninterrupted power tomotor 220 during power source exchanges (e.g., switching from externalbattery 145 to power adapter 155, removing both external battery 145 andpower adapter 155, or other combinations thereof). In one embodiment,the primary power source for system controller 125 is one of externalbattery 145 and power supply 155. In one embodiment, a secondary powersource (e.g., battery 230, which can be a lithium-ion battery) isintegrated within the main body of system controller 125 housing.Removal of either of the primary power sources automatically causessystem controller 125 to switch to internal battery 230 for power suchthat there is no interruption of motor drive controller 220 and pump110.

In one embodiment, internal battery 230 provides uninterrupted operationfor system controller 125 and pump 110 when all external power sources(e.g., external battery 145 or power adapter 155) are decoupled fromsystem controller 125. Internal battery 230 allows system controller 125and pump 110 to withstand the failure, or removal of all external powersources. For example, in certain situations a user or patient may preferto remove all external devices and external battery packs to achievemaximum portability of system controller 125.

FIG. 5 illustrates, as a three-dimensional drawing, an exemplary systemcontroller 125′. In one embodiment, system controller 125′ includesintegrated infrared port 510 protected by a translucent window. Theinfrared port 510 can be implemented as part of infrared hardware 216shown in FIG. 2. In one embodiment, system controller 125′ connects toexternal battery 145 that also contains an infrared port behind awindow. In one embodiment, infrared port on external battery 145 can beimplemented as part of infrared hardware 316 shown in FIG. 3. Systemcontroller 125′ has one or more power connections to couple systemcontroller 125′ to an external source of power. System controller 125′can have separate power connections to connect to an external battery aswell as to connect to a power adapter. In one embodiment, systemcontroller 125′ has one or more power connections 505 and 515 to enableconnection to external battery 145.

FIG. 6 illustrates, as a three-dimensional drawing, an exemplary systemcontroller 125′ coupled to an exemplary external battery 145′. In oneembodiment, system controller 125′ has power connection 130′ separatefrom external battery 145′ connection 605. In one embodiment, systemcontroller 125′ contains recessed area 535 above infrared port 510 toreceive an overhang or lip 620 from external battery 145′ to furthershield infrared port 510 from outside interference when systemcontroller 125′ and external battery 145′ are communicatively coupled.

In one embodiment, external battery 145′ includes integrated touchscreen 610, and breakaway connection 605 to enable external battery 145′to couple to power adapter 155 or other power source. In one embodiment,breakaway connection 605 integrated into external battery 145′ is aseparate connection from system controller breakaway connection port130′. In one embodiment, power adapter breakaway connection 605 onexternal battery 145′ and breakaway connection 130′ on system controller125′ are able to receive the same or compatible connector/plug frompower adapter 155 or other external power source. System controller 125′also contains port 120′ that couples drive line 115′ to systemcontroller 125′. In one embodiment, drive line port 120′ is a separatecomponent and is physically incompatible with breakaway connection ports130′ and 605.

In one embodiment, power connections 505 and 515 coupling systemcontroller 125′ and external battery 145′ together are one or more of anelectromagnet, magnet, and mechanical connection (herein after simplyreferred to as a breakaway power connection). In one embodiment,breakaway power connections 130′ and 605 from power adapter 155 connectdirectly to system controller 125′ housing and no power leads arerequired. In one embodiment, breakaway power connections 505 and 515connect external battery 145′ directly to system controller 125′ housingand no power leads or cables are required.

Breakaway power connections minimize trauma to the exit site if systemcontroller 125′ is dropped, external battery 145′ or power adapter 155is forcibly pulled from system controller 125′, or other stress isapplied to one or more of the individual VAS components. At apredetermined force, the breakaway power connections between the VAScomponents separate (i.e., decouple) such that only the weight of systemcontroller 125′ acts on drive line 115′ and the exit site. Stress ondrive line 115′ often directly leads to stress at the exit site wheredrive line 115′ enters the patient. Lowering the risk of traumaexperienced by the exit site lowers the potential risk for infection tothe patient.

In one embodiment, the breakaway power connections use passive or active(e.g., electromagnetic) magnets to control the sequence of devices thatdisconnect when external stress is applied to any of the coupled VAScomponents. For example, a patient may get a line or component caught onan object while walking, and the breakaway power connection ensures theexternal battery separates before causing external stress to the exitsite. In one embodiment, the passive or active magnets further comprisesecondary mechanical features to restrain the transverse movements ofthe power connections. In other embodiments, the breakaway powerconnection is a slide rail mechanical connection or a combination of allpreviously mentioned connections. In one embodiment, system controller125′ automatically switches to internal power when an external source ofpower (e.g., external battery 145′ or power adapter 155) is lost or hasa fault condition.

FIG. 22 illustrates a perspective view of one embodiment of a poweradapter 2200 with breakaway power connections. In one embodiment, poweradapter 2200 has one or more magnets (e.g., magnet 2201 and 2205) thatcan be mechanically coupled to magnets in system controller 125. In oneembodiment, the one or more magnets (e.g., magnet 2201 and 2205) havedifferent (e.g., opposite) polarity relative to other magnets in poweradapter 2200. For example, magnet 2201 can have a first polarity (e.g.,South) and magnet 2205 can have a reverse polarity (e.g., North), orvice versa. In one embodiment, the one or more magnets are separatephysical connections from power connections 2202 and 2203 that provide(e.g., conduct) power to system controller 125 or external battery 145.In other embodiments, a magnet is integrated into the power connection(e.g., integrated into power connection 2202 or 2203). In oneembodiment, system controller 125 and external battery 145 have similaror identical components to allow for coupling to power adapter 2200. Inone embodiment, power adapter 2200 and system controller 125 havemechanical components (e.g., slide rails) to align the connections(e.g., power pins 2206) and magnets to a targeted point of contact. Inone embodiment, power adapter 2200 has an integrated overhang or lip2204 to cover the infrared port of the system controller when the systemcontroller and power adapter are mechanically coupled together.

In one embodiment, the force required to decouple a breakaway powerconnection is predetermined such that an axial loading event applied toboth external battery 145′ and power adapter 155 cause power adapter 155to decouple first. Pre-configuring the force required for each breakawayconnection allows system controller 125′ to exert minimal force on thepercutaneous cable while also providing a predetermined breakawaysequence. In one embodiment, external battery 145′ is coupled to poweradapter 155 as well as system controller 125′.

In one embodiment, when more than two devices (e.g., system controller,battery, and power adapter) are connected together, an ordered breakawayevent is possible. For example, in the event of a force (e.g., aphysical force, mechanical force, pull or tug) on drive line 115′ orpower adapter 155 cable, power adapter 155 is the first device todecouple from a component in the VAS. If there is further or increasedforce on drive line 115′, external battery 145′ detaches from systemcontroller 125′. In one embodiment, the magnet strength in eachbreakaway connection is predetermined to enforce a specific breakawayorder or sequence. For example, the magnets coupling power adapter 155to system controller 125 can be less magnetic (e.g., lowerstrength/attraction), than the magnets coupling external battery 145 andsystem controller 125.

In one embodiment, one or more of the magnets is an electromagnet. Inone embodiment, an electromagnet is integrated into the power connectionused for coupling and decoupling power adapter 155 (AC or DC) to systemcontroller 125. In one embodiment, the same power connection with anintegrated electromagnet is also used to couple power adapter 155 toexternal battery 145. In one embodiment, as power adapter 155 orexternal battery 145 approaches system controller 125, a magneticallyactivated relay in power adapter 155 or external battery 145 istriggered by a specially located magnet. In one embodiment, thespecially located magnet is in one or more of system controller 125,external battery pack 145, and power adapter 155. In one embodiment,activating/triggering the magnetic switch also activates/triggers theelectromagnet at one or more of the connections on system controller125, external battery 145 or power adapter 155 (e.g., an AC or DC poweradapter). In one embodiment, activating/triggering the electromagnetincreases the attractive magnetic force between the one or more systemcomponents (e.g., power adapter, external battery and systemcontroller). Increasing the electromagnetic force increases the pullbetween components and also helps in aligning the coupled components. Inone embodiment, the electromagnet is powered briefly to reduce powerconsumption.

In one embodiment, when the magnetic switch is deactivated/disengaged(e.g., because power adapter 155 or external battery 145 is no longer inclose proximity to system controller 125) the electromagnet reversescurrent, negating the magnetic field from the internal magnets. Negatingthe magnetic field facilitates the breakaway process of the connectedcomponents when the components are subjected to a force (e.g., cord pullor excessive twisting).

In one embodiment, the mechanical features facilitating the coupling ofsystem 125 prevents transverse motion or shearing between systemcontroller 125 and other connected devices and does not prevent orrestrain the axial position of connected modules.

Redundant and Flexible Alert Delivery

In one embodiment, system controller 125 implements one or more types ofalarms (e.g., visual, audible, and/or vibratory). Alarm data associatedwith an alarm can be one or more of a hazard, alert, notification orevent. Alarms can be represented on touch screen 330 as one or more ofvisual text, icons, images, video, charts, and graphs. In oneembodiment, the alarms on system controller 125 are mirrored(duplicated) on external battery touch screen 330. Visual alarminformation on external battery touch screen 330 can also include textdescriptions of the alarm in a choice of one or more languages. Alarminformation can also include recommendations to fix the cause of thealarm, or ways to quiet/disable an alarm. For example, display 240 canpresent a recommendation for the user of the device to contact atechnician or recommendations for servicing (e.g., the connections onsystem controller 125 have an error, or the infrared window needscleaning). In one embodiment, alarms are displayed as text messages,lights or icons displayed on system controller 125. In one embodiment,the vibratory alerts supplement the audible and visual alarms forhazards and advisories. In one embodiment, system controller 125 andexternal battery pack 145 store alarm history in memory 205 and memory305, respectively.

In one embodiment, system controller 125 sends alerts or statusinformation to external device 270 and/or external battery 145. In oneembodiment, external battery 145 and/or an external device 270 providesreal time mirroring of alerts provided by system controller 125. As usedherein, mirroring of an alarm duplicates the alarm data provided bysystem controller 125 to another external device 270 and/or externalbattery 145. For example, if pump 110 error is detected by systemcontroller 125, an alarm on system controller 125 is set on systemcontroller 125 as well as on external device 270 and/or external battery145. Mirroring of alarms insures that important system information isconveyed to the patient despite a failure of the alarm output on one ofthe system components. For example, if an alarm sounds on systemcontroller 125 when the speed of the motor reaches an unacceptably lowlevel, a representation of the alarm data is displayed on systemcontroller 125 as another representation of the alarm data is displayedon external battery 145. In another example, system controller 125 canprovide one or more alarms to notify the patient of the low batterylevel of internal battery 230. In one embodiment, alarms on systemcontroller 125 are represented by one or more LEDs.

In one embodiment, external battery 145 also implements one or morealarms (e.g., visual, audible, and vibratory) and also provides alertsfor battery 320 as well as system controller's internal battery 230. Inother embodiments, external battery 145 monitors its own battery leveland can provide an alarm based on an independent determination ofbattery status separate from system controller 125.

In one embodiment, alarm 245 on system controller 125 is the primaryalarm system to provide alarm notification at all times regardless ofthe presence of external battery 145 and alarm 335. In otherembodiments, alarm 245 on system controller 125 is not activated whilealarm 335 on external battery 145 is active. In one embodiment, an alarmoccurs only on external battery 145 when the alarm is only associatedwith integrated battery 320. In one embodiment, alarms associated withintegrated battery 320 occur when external battery 145 is decoupled fromsystem controller 125. Alarms can also occur during the coupling ordecoupling of external battery 145 to/from system controller 125 orpower adapter 155. In one embodiment, external battery 145 alarm 335receives alarm data from system controller 125 by an infraredcommunications link. Alarm data can be used to synchronize timing andlogs associated with alarms on system controller 125 and externalbattery 145.

In one embodiment a fall or impact recorded by an accelerometerintegrated into system controller 125 or external battery 145 isrecorded and represented as an alarm. A fall or impact can also befollowed by a series of questions to the user displayed on the externalbattery touch screen.

External Battery and System Controller Infrared Communication

In one embodiment, system controller 125 communicates with externalbattery 145 and/or other detachable device using an infraredcommunications link (e.g., IrDA). Implementing an infraredcommunications link to connect system controller 125 and externalbattery 145 provides for robust wireless communications between systemcontroller 125 and external battery pack 145. Infrared communicationdoes not occupy bandwidth in frequency ranges regulated by the FederalCommunications Commission (FCC). Furthermore, using infrared reduces oreliminates errors and failures associated with other forms of wirelesscommunication (e.g., electrostatic discharge, electromagneticinterference, or other naturally occurring electromagnetic phenomenon onthe physical communications hardware). In addition, an infrared port,such as infrared port 510 window is easily cleaned and maintained byuntrained operators and allows for a waterproof system controller 125.Incorporating an infrared port as opposed to an Ethernet or otherexposed electrical ports facilitates a waterproof enclosure design whileretaining robust mechanical design (i.e., fewer mechanical parts; noelectromechanical connector). Through sealing of the infrared port andother novel features described in this application (e.g., intelligentpower disconnects), it is possible to manufacture system controller 125such that it is completely waterproof and meets IP68 (Ingress ProtectionRating) standards. In other embodiments, external battery 145 alsocontains an infrared port and is water resistant.

In one embodiment, when system controller 125 and external battery pack145 are in close proximity to each other, a switch is triggered oractivated in system controller 125. In one embodiment, the switch is amagnetic switch (e.g., a reed switch or Hall effect switch) which can beconsidered to be a form of a proximity sensor. In other embodiments, themagnetic switch is located in external battery pack 145. Upon detectingthat the magnetic switch is triggered, external battery pack 145initiates communications with the system controller 125. In otherembodiments, upon detecting that the magnetic switch is triggered,system controller 125 initiates communication with external battery pack145. In one embodiment, infrared communication is used to link externalbattery 145 and system controller 125. In one embodiment, a user caninitiate and/or acknowledge infrared data links and transfers with touchscreen 330 on external battery 145. For example, to connect systemcontroller 125 to a base station, an icon or representation ofinitiating a connection is provided on touch screen 330. In oneembodiment, no pump controls are available on touch screen 330 in orderto separate the most important functions of system controller 125 fromexternal influence.

FIG. 7 is a flow chart illustrating an exemplary method 700 forconnecting external battery 145 to system controller 125. For example,method 700 may be performed by external battery 145 and systemcontroller 125. For the sake of simplicity, it is assumed that method700 is performed by system controller 125.

At block 705, the magnetic switch (or other proximity sensor) in systemcontroller 125 is “open” and has not been triggered by any closeproximity magnet (or other trigger such as light if a light sensor isused).

At block 710, the output power terminals (e.g., output connections 505and 515) of system controller 125 are decoupled such that they cannotreceive or send power.

At block 715, system controller 125 determines whether the magneticswitch is in a “closed” state. For example, the proximity of externalbattery 145 triggers the magnetic switch of system controller 125 sothat the switch enters the “closed” state. If the switch remains open,the method 700 returns to block 710 and no power is output to theterminals.

At block 720, system controller 125 determines whether an infraredconnection to external battery 145 is established. If no infraredconnection is detected, the output power terminals remain decoupled.

At block 725, system controller 125 determines that an infraredconnection exists with external battery 145 and system controller 125determines whether an external fault is detected. If an external faultis detected, method 700 returns to block 710 and no power is output tothe terminals.

At block 730, system controller 125 determines no external fault isdetected, and allows DC power on the output terminals.

At block 735, system controller checks whether the magnetic switch is“open.” If the magnetic switch is “open” method 700 returns to block 710and no power is output to the terminals. Otherwise, method 700 checksfor faults at block 725 and maintains power if no fault is detected.

System controller 125, upon detecting an enabled connected externalbattery 145, begins a handshaking routine that both identifies itselfand allows the external battery 145 to receive and record data fromsystem controller 125. When external battery 145 is separated fromsystem controller 125, the magnetic switch in the external battery 145is triggered or deactivated and the infrared communications from theexternal battery 145 is discontinued.

In one embodiment, the frequency range of the infrared communication isbetween the FCC regulated portion of the RF (radio frequency) spectrumand the visible light spectrum (e.g., approximately within the range of860 nm-940 nm). At this wavelength, an infrared transmitter transmitsdata in a point-to-point fashion. Moreover, an infrared transmitter doesnot emit nor interferes with radio frequency or microwave transmissions.In one embodiment, when system controller 125 and external battery 145are mechanically coupled the infrared transceiver units are physicallyshielded from outside interference. In one embodiment, an overhang orlip on external battery 145 or system controller 125 provides physicalshielding over the transceiver units. Physically shielding the infraredports ensures that nearby devices cannot intercept data transmittedbetween system controller 125 and the external battery 145. Furthermore,shielding the connections prevents external infrared sources, such asheating equipment, from interfering with the communications betweensystem controller 125 and external battery 145. In one embodiment, awindow (e.g., polycarbonate tinted material) embedded in the enclosurehousing covers the infrared transceivers in external battery 145 andsystem controller 125. In one embodiment, the window cover protects thetransceivers from water, dust, and other potentially damaging elements.In one embodiment, the window is easily cleaned with readily availablehousehold or hospital-grade solvent. Untrained users or patients,therefore, are able to easily clean the window to remove any accumulateddebris or film.

Users or patients may easily and inadvertently damage electricalcontacts or exposed components. Utilizing a wireless communicationssystem eliminates the requirement for electrical contacts or exposedcomponents in the communications system. The flush window cover alsoallows the enclosure to be made waterproof compliant with IP68 ratings.In one embodiment, the window placed inside the housing enclosurematerial while it is being manufactured creates a watertight window asthe enclosure material forms around it. The window material can bemanufactured from plastic that is transparent at infrared frequenciesbut nearly opaque at visible light frequencies.

FIG. 8 is a flow chart illustrating method 800 for transferring dataacross an infrared data connection between a first and second detachabledevice according to one embodiment. In one embodiment, the firstdetachable device is system controller 125, and the second detachabledevice is external battery 145 or power adapter 155. For example, method800 can be performed by the first detachable device. In one embodiment,a proximity sensor (e.g., a magnetic switch) on the first detachabledevice senses the proximity of the second device. In response, the firstdetachable device activates (e.g., starts up) an infrared connectionbetween the two devices before the second detachable device is allowedto provide power to the first detachable device.

At block 805, the first detachable device establishes an infrared dataconnection between the first detachable device and the second detachabledevice.

At block 810, the first detachable device transfers data, through aninfrared connection, between the first detachable device and the seconddetachable device. In one embodiment, the first detachable devicereceives the data sent from the second detachable device. In otherembodiments, the second detachable device receives data sent from thefirst detachable device. In yet other embodiments, both the first andsecond detachable devices send and receive data.

At block 815, the first detachable device enables power from the seconddetachable device to the first detachable device. In one embodiment,power is only provided after a data connection between the first andsecond detachable devices has been established.

External batteries and the connections on system controller 125 cansometimes be exposed to outside elements. In one embodiment, systemcontroller 125 and external battery 145 decouple their internal DC powerconnections, such that no power can flow through the externally exposedpower connections. Disconnecting power connections until confirmation ofa proximity sensor and an infrared connection insures that accidentalpower shorting is unlikely to occur. For example, a patient mightaccidentally connect the power connections 135 and 130 while systemcontroller 125 or external battery 145 touches keys or coins in a pocketor after contact with water. If the exposed connections are exposed toany conductive material a short can occur that can impact vital systemcomponents or shock the patient. In one embodiment, requiring one ormore of the triggering of a proximity sensor and establishing aninfrared connection before coupling the DC power connections greatlyreduces the risk of damage or shock to system components and thepatient.

FIGS. 9 through 38 illustrate various embodiments of the componentsdiscussed herein. Specifically, FIGS. 9 through 11 illustrate a systemcontroller coupled to an external battery pack and percutaneous leadaccording to one embodiment. FIGS. 12 through 16 illustrate oneembodiment of a system controller coupled to a power adapter andpercutaneous lead. FIGS. 17 and 18 illustrate one embodiment of a systemcontroller coupled to a percutaneous lead and decoupled from a poweradapter. FIGS. 19 and 20 illustrate a power adapter according to oneembodiment. FIGS. 21 through 26 illustrate one embodiment of a poweradapter having magnetic connections and power connections. FIG. 27 is anexploded view illustrating one embodiment of a power adapter havingmagnetic connections and power connections. FIG. 28 is an exploded viewillustrating a power adapter power cable, power connections, andmagnets, according to one embodiment. FIG. 29 illustrates one embodimentof a power adapter power cable, power connections, and magnets. FIGS. 30through 33 illustrate one embodiment of a power adapter powerconnection. FIGS. 34 through 36 illustrate a power adapter havingmagnetic connections and power connections, according to one embodiment.FIG. 37 is a perspective view illustrating one embodiment of a poweradapter power cable housing. FIG. 38 is a partial perspective viewillustrating one embodiment of a power adapter power cable housing.

Various embodiments and aspects of the inventions have been describedabove with reference to the accompanying drawings. The foregoingdescription and drawings are illustrative of the invention and are notto be construed as limiting the invention. Numerous specific detailshave been described to provide a thorough understanding of variousembodiments of the present invention. However, in certain instances,well-known or conventional details have been omitted in order to providea concise discussion of embodiments of the present inventions. It willbe evident that various modifications may be made thereto withoutdeparting from the broader spirit and scope of the invention as setforth in the following claims.

Reference in the specification to one embodiment or an embodiment meansthat a particular feature, structure or characteristic described inconnection with the embodiment is included in at least one embodiment ofthe invention. The appearance of the phrase “in one embodiment” invarious places in the specification do not necessarily refer to the sameembodiment.

An article of manufacture may be used to store program code providing atleast some of the functionality of the embodiments described above. Anarticle of manufacture that stores program code may be embodied as, butis not limited to, one or more machine readable non-transitory storagemedia such as memories (e.g., one or more flash memories, DRAM, randomaccess memories—static, dynamic, or other), optical disks, CD-ROMs,DVD-ROMs, EPROMs, EEPROMs, magnetic or optical cards or other type ofmachine-readable non-transitory media suitable for storing electronicinstructions. Additionally, embodiments of the invention may beimplemented in, but not limited to, hardware or firmware utilizing anFPGA, ASIC, a processor, a computer, or a computer system including anetwork. Modules and components of hardware or software implementationscan be divided or combined without significantly altering embodiments ofthe invention. The specification and drawings are, accordingly, to beregarded in an illustrative sense rather than a restrictive sense.

1. A machine-implemented method of operating a medical device system,comprising: establishing an infrared data connection between aprocessing system which is coupled to a battery and a detachable device,wherein the processing system receives data from or provides data to thedetachable device using the infrared data connection; receiving datafrom a proximity sensor, the data indicating whether the detachabledevice is attached to the battery and the processing system; providingpower from the battery to the detachable device which is adapted to becoupled to a patient.
 2. The method as in claim 1, wherein the proximitysensor is a magnetic switch.
 3. The method as in claim 1, wherein thedetachable device includes a battery in the detachable device andwherein the data received from the detachable device represents a statusof the detachable device or the battery in the detachable device.
 4. Themethod as in claim 3 wherein the status is one or more of: alarm status,event history, pump parameters, log data, and power source status. 5.The method as in claim 1 wherein the proximity sensor is coupled to theprocessing system and wherein data from the proximity sensor causes theprocessing system to attempt to exchange data with the detachabledevice.
 6. The method as in claim 5 wherein the data from the proximitysensor initiates the infrared data connection.
 7. The method as in claim4 wherein the detachable device automatically switches to the battery inthe detachable device when the battery is decoupled from the detachabledevice.
 8. The method as in claim 4 wherein the status is displayed on atouchscreen that is coupled to the processing system and to the battery.9. The method as in claim 6 wherein power is provided from the batteryto the detachable device in response to successfully establishing theinfrared data connection.
 10. The method as in claim 3 wherein thedetachable device is a system controller for a medical device adapted tobe coupled to the patient.
 11. A medical device system comprising: afirst housing; a processing system coupled to a battery and to a firstinfrared data port, the processing system, the battery and the firstdata port disposed in the first housing; a detachable device whichincludes a second housing, an internal battery and a second infrareddata port coupled to the internal battery, the processing systemconfigured to establish an infrared data connection between theprocessing system and the detachable device, the infrared dataconnection exchanges data between the processing system and thedetachable device, and wherein the processing system and the battery areconfigured to provide power from the battery to the detachable device.12. The system as in claim 11, further comprising a proximity sensor onthe first housing, the proximity sensor configured to provide data tothe processing system, the data indicating whether the detachable deviceis attached to the first housing.
 13. The system as in claim 12 whereinthe proximity sensor is a magnetic switch.
 14. The system as in claim 12wherein data received from the detachable device, through the infrareddata connection, represents a status of the detachable device or theinternal battery.
 15. The system as in claim 14 wherein the status isone or more of: alarm status, event history, pump parameters, log data,and power source status.
 16. The system as in claim 12 wherein data fromthe proximity sensor causes the processing system to attempt to exchangedata through the infrared data connection.
 17. The system as in claim 16wherein the data from the proximity sensor initiates the infrared dataconnection.
 18. The system as in claim 12 wherein the detachable deviceautomatically switches to the internal battery when the detachabledevice is decoupled from the first housing.
 19. The system as in claim12 further comprising: a touchscreen disposed on the first housing andcoupled to the processing system and the battery.
 20. The system as inclaim 12 wherein power is provided from the battery to the detachabledevice in response to successfully establishing the infrared dataconnection.
 21. The system as in claim 12 wherein the detachable deviceis a system controller for a medical device.